Smart point of presence (spop) aircraft-based high availability edge network architecture

ABSTRACT

A high availability aircraft network architecture incorporating smart points of presence (SPoP) is disclosed. In embodiments, the network architecture divides the aircraft into districts, or physical subdivisions. Each district includes one or more mission systems (MS) smart network access point (SNAP) devices for connecting MS components and devices located within its district to the MS network. Similarly, each district includes one or more air vehicle systems (AVS) SNAP devices for connecting AVS components and devices within the district to the AVS network. The AVS network may remain in a star or hub-and-spoke topology, while the MS network may be configured in a ring or mesh topology. Selected MS and AVS SNAP devices may be connected to each other via guarded network bridges to securely interconnect the MS and AVS networks.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and claims the benefit of theearliest available effective filing dates from the following listedapplications (the “Related Applications”) (e.g., claims earliestavailable priority dates for other than provisional patent applications(e.g., under 35 USC § 120 as a continuation in part) or claims benefitsunder 35 USC § 119(e) for provisional patent applications, for any andall parent, grandparent, great-grandparent, etc. applications of theRelated Applications).

Related Applications

Concurrently filed U.S. patent application Ser. No. ______ entitledSMART POINT OF PRESENCE (SPoP) DEVICES FOR AIRCRAFT-BASED HIGHAVAILABILITY EDGE NETWORK ARCHITECTURE and having internal docket number124850US03; and

U.S. Provisional Patent Application Ser. No. 62/915,556 entitled SMARTPOINT OF PRESENCE (SPOP) FOR AIRCRAFT-BASED HIGH AVAILABILITY EDGENETWORK ADAPTATION, filed Oct. 15, 2019;

Said U.S. patent application Ser. No. ______ and 62/915,556 are hereinincorporated by reference in their entirety.

TECHNICAL FIELD

Embodiments of the inventive concepts disclosed herein are directedgenerally to computer networking, and particularly to avionicsnetworking configurations incorporating mission-critical subsystems.

BACKGROUND

Mission systems updates aboard aviation assets may require a long timeto build, test, and certify. Current network architectures areoptimized, with size, weight, and power (SWaP) considerations in mind,into interwoven “safe flight” and “mission success” systems. While itmay be possible to separate architectures into independent, interactiveair vehicle systems (AVS) and mission systems (MS) subsystems, theunderlying “hub and spoke” network topologies require long wiring runs(doubly so in the case of duplex systems) which translates to increasedwire weight, high rewiring costs, and high I/O density at the hubs,which complicate LRU designs and may require additional switches toextend the network topology.

Current interwoven architectures may require lengthy testing in order toachieve airworthiness certification. However, mission systems may besubject to far more rapid change and update cycles than air vehiclesystems. While the emergence of autonomous systems may in turn requiremore redundant systems, legacy input/output (I/O) and power systems willpersist as components of the solution space for the foreseeable future,as there is as yet no “one size fits all” I/O or power solution capableof supplanting them.

SUMMARY

A high availability aircraft network architecture incorporating smartpoints of presence (SPoP) is disclosed. In embodiments, the networkarchitecture divides the aircraft into districts, or physicalsubdivisions. Each district includes one or more mission systems (MS)smart network access point (SNAP) devices for connecting MS componentsand devices located within its district to the MS network. Similarly,each district includes one or more air vehicle systems (AVS) SNAPdevices for connecting AVS components and devices within the district tothe AVS network. The MS network and AVS network may be interconnectedbut configured according to different topologies. Selected MS and AVSSNAP devices may be connected to each other via guarded network bridgesto securely interconnect the MS and AVS networks.

In some embodiments, the network architecture includes at least oneessential district wherein the MS SNAP device and/or AVS SNAP device areconnected to at least one essential (e.g., mission-critical) component.

In some embodiments, the MS network is configured according to a ring ormesh topology, and the AVS network is configured according to ahub-and-spoke or star topology.

In some embodiments, the MS SNAP devices of the MS network are connectedvia fiber optic network trunk.

In some embodiments, the MS network includes at least one MS SNAP deviceincorporating an adaptive input/output (I/O) component connecting the MSSNAP device to legacy I/O or power components within the district (e.g.,connecting legacy wired devices to the fiber optic MS network) andproviding for data exchange between the legacy I/O or power componentsand the MS network.

In some embodiments, the legacy I/O or power components includecomponents or devices connected via MIL-STD-1553 serial data bus, ARINC429 avionics data bus, or Ethernet networking cables or components.

In some embodiments, the adaptive I/O components includes a dataconcentrator unit (DCU).

In some embodiments, the adaptive I/O component incorporates across-domain data guard and multiple levels of security (MLS)encryption/decryption modules.

In some embodiments, the MS SNAP device includes power controlcomponents configured for distributing operating power to MS componentswithin the district connected to the MS SNAP device.

In some embodiments, the power control components are selected from apower converter connected to an aircraft power supply, electroniccircuit breakers (ECB) configured for providing converted power to MScomponents, and local batteries for supplying power directly to MScomponents.

This Summary is provided solely as an introduction to subject matterthat is fully described in the Detailed Description and Drawings. TheSummary should not be considered to describe essential features nor beused to determine the scope of the Claims. Moreover, it is to beunderstood that both the foregoing Summary and the following DetailedDescription are example and explanatory only and are not necessarilyrestrictive of the subject matter claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. The use of the same reference numbers in different instances inthe description and the figures may indicate similar or identical items.Various embodiments or examples (“examples”) of the present disclosureare disclosed in the following detailed description and the accompanyingdrawings. The drawings are not necessarily to scale. In general,operations of disclosed processes may be performed in an arbitraryorder, unless otherwise provided in the claims. In the drawings:

FIG. 1 is a diagrammatic illustration illustrating a networked aircraft,in accordance with example embodiments of this disclosure;

FIG. 2 is a diagrammatic illustration illustrating air vehicle systems(AVS) and mission systems (MS) networks of the aircraft of FIG. 1;

FIG. 3 is a diagrammatic illustration illustrating components of the AVSand MS networks of the aircraft of FIG. 1;

FIG. 4 is a diagrammatic illustration of components of the MS network ofFIG. 3;

FIG. 5 is an isometric view of a smart network access point (SNAP)device of the AVS and MS networks of FIGS. 1 through 3;

FIG. 6 is an isometric view of an adaptive I/O access point (AIAP)device of the AVS and MS networks of FIGS. 1 through 3;

FIGS. 7A and 7B are block diagrams of components of the SNAP device ofFIG. 5;

FIG. 7C is a block diagram of components of the SNAP device of FIG. 5and the AIAP device of FIG. 6;

FIG. 7D is a block diagram of components of the AIAP device of FIG. 6;

FIGS. 8A and 8B are block diagrams of components of the SNAP device ofFIG. 5 and the AIAP device of FIG. 6;

FIG. 9 is a block diagram of components and operations of the AIAPdevice of FIG. 6;

and FIG. 10 is a block diagram of an implementation of the AIAP deviceof FIG. 6.

DETAILED DESCRIPTION

Before explaining one or more embodiments of the disclosure in detail,it is to be understood that the embodiments are not limited in theirapplication to the details of construction and the arrangement of thecomponents or steps or methodologies set forth in the followingdescription or illustrated in the drawings. In the following detaileddescription of embodiments, numerous specific details may be set forthin order to provide a more thorough understanding of the disclosure.However, it will be apparent to one of ordinary skill in the art havingthe benefit of the instant disclosure that the embodiments disclosedherein may be practiced without some of these specific details. In otherinstances, well-known features may not be described in detail to avoidunnecessarily complicating the instant disclosure.

As used herein a letter following a reference numeral is intended toreference an embodiment of the feature or element that may be similar,but not necessarily identical, to a previously described element orfeature bearing the same reference numeral (e.g., 1, 1 a, 1 b). Suchshorthand notations are used for purposes of convenience only and shouldnot be construed to limit the disclosure in any way unless expresslystated to the contrary.

Further, unless expressly stated to the contrary, “or” refers to aninclusive or and not to an exclusive or. For example, a condition A or Bis satisfied by any one of the following: A is true (or present) and Bis false (or not present), A is false (or not present) and B is true (orpresent), and both A and B are true (or present).

In addition, use of “a” or “an” may be employed to describe elements andcomponents of embodiments disclosed herein. This is done merely forconvenience and “a” and “an” are intended to include “one” or “at leastone,” and the singular also includes the plural unless it is obviousthat it is meant otherwise.

Finally, as used herein any reference to “one embodiment” or “someembodiments” means that a particular element, feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment disclosed herein. The appearances of thephrase “in some embodiments” in various places in the specification arenot necessarily all referring to the same embodiment, and embodimentsmay include one or more of the features expressly described orinherently present herein, or any combination or sub-combination of twoor more such features, along with any other features which may notnecessarily be expressly described or inherently present in the instantdisclosure.

Embodiments of the inventive concepts disclosed herein are directed to anetwork architecture based on localized smart points of presence (SPoP)and incorporating autonomous, interconnected air vehicle systems (AVS)and mission systems (MS) communications networks which are distinctlyseparable and protected while remaining highly interactive with eachother through a “digital backbone”. While in the short term the AVSnetwork, which is associated with a lower change velocity, may remain atraditional hub-and-spoke (e.g., point-to-point, star-topology) networkwith a high-speed, high-bandwidth network trunk, the MS network (whichhas a much higher change velocity) may adopting ring or mesh topologiesto increase reliability, survivability, availability, and alleviate theneed for long wiring runs. In some embodiments, the AVS network mayadditionally adopt ring/mesh topologies. The MS and AVS network trunksmay incorporate copper or other cabling (e.g., to accommodate legacy I/Oor power components); alternatively, the network trunks may be fiberoptic based.

Referring to FIGS. 1 and 2, the aircraft 100 is shown. The aircraft 100may include, but is not limited to, fixed-wing craft, rotorcraft, orunmanned aircraft systems (UAS) piloted by one or more remote operators,or capable of partially or fully autonomous operation.

In embodiments, the aircraft 100 may be compartmentalized and/orcategorized into districts, each district corresponding to a physicalsubdivision of the aircraft and incorporating any and all networkcomponents physically located within the said district. Each districtmay include one or more district service access points (DSAP) throughwhich any network components within the district may be connected to,and may exchange data with, an MS or AVS network.

In embodiments, the aircraft 100 may be broken down into essentialdistricts 102 and non-essential districts 104. Essential districts 102may include AVS essential districts and MS essential districts; AVSessential districts may support equipment and/or services directed toaviation functions, while MS essential (and non-essential) districts maysupport mission-related equipment and/or services. For example, AVSnetwork components or services may include, but are not limited to,flight control and/or air vehicle computers, human/machine interfaces(HMI), autonomous command and control (C2) and payload systems,communications antennas and tuners, standby instrumentation, landinggear and lighting control systems, vehicle management sensors (e.g.,engine, transmission, fuel), and onboard navigational instruments (e.g.,radar altimeter (radalt), VOR/ILS, air data computers (ADC), embeddedGPS/inertial (EGI) positioning systems). MS network components andservices may include, but are not limited to, mission computers and/ordisplay systems (e.g., including DVE processing systems and/or 3Dsensors), flight/mission data recorders, weather sensors and/orreceivers, head-mounted display (HMD) systems and head trackers, weaponsand targeting systems, survivability components and countermeasures, andtactical communications systems (e.g., LOS/BLOS radio systems, SATCOMradio systems, tactical data links). “Essential” equipment or servicesmay refer to any mission-critical network component incorporating dualredundancies (e.g., to avoid a single point of failure and ensure highavailability) and/or any network component operating or operable onlocal battery power (as described in greater detail below). Similarly,non-essential network components include any network components that arenot essential, e.g., without which mission objectives may be fulfilledvia alternative means.

In embodiments, essential districts 102 may include both essential andnon-essential components, while non-essential districts 104 supportsolely non-essential components. Referring in particular to FIG. 2, theaircraft 100 may incorporate an AVS network 202 having a star topology(e.g., hub-and-spoke) comprising a number of smart network access point(SNAP) devices 204, each SNAP device connected to a central/hub SNAPdevice 204 a via AVS network trunk 206 (e.g., fiber optic, copper/wiredor cable connection) and serving as a DSAP for any AVS networkcomponents or devices within its district. Similarly, the aircraft 100may incorporate an MS network 208 comprising a group of SNAP devices 204connected in a ring topology via an MS network trunk 210 (e.g., fiberoptic trunk cable). For example, the AVS network 202 and MS network 208may be independent and isolated from each other but directly connectedvia one or more network bridges 212 (e.g., dual redundant guard/networkbridge). In embodiments, each district (essential districts 102 andnon-essential districts 104) may include at least one SNAP device 204,e.g., at least one AVS SNAP device of the AVS network 202 and at leastone MS SNAP device of the MS network 208. For example, some districtsmay include multiple SNAP devices, e.g., if the quantity of networkcomponents and/or devices within its district so requires.

By moving hub-and-spoke connections of the AVS network 202 to thedistrict level, the length (and weight) of cabling or wiring may beminimized while maintaining high availability. Similarly, anext-generation or high change velocity MS network 208 may beretrofitted to an existing hub-and-spoke AVS network 202, allowing forhigh flexibility of functionality by supporting the addition of new SNAPdevices 204 between existing MS SNAP devices in an MS network having aring topology (e.g., or a mesh topology). Further, SNAP devices 204 mayprovide conversion support for legacy I/O and/or power components at thedistrict level, compartmentalizing I/O and power needs within a districtand providing for easier portability of features from one SNAP device toanother. The replacement of legacy I/O and power components may beincentivized by the removability of conversion support features whenthey are no longer needed, further improving SWaP considerations. At ahigh level, rapid change and deployment of new MS features may beprovided while preserving certified airworthy AVS features, eliminatingthe need for additional recertification testing.

Referring to FIG. 3, the aircraft 100, AVS network 202, and MS network208 are disclosed.

In embodiments, the AVS network 202 and MS network 208 may be connectedvia high bandwidth network bridges 212 (e.g., dual redundant networktrunks) protected on each end by SNAP devices 204 and including assurednetwork guards. For example, the network bridges 212 may further providea “digital backbone” for additional shared functionalities (e.g.,adaptive cooling/thermal management for dissipation or control of heatgenerated by components within a district) between the AVS and MSnetworks.

In embodiments, each SNAP device 204 may serve as a district serviceaccess point (DSAP) for network components in its district. For example,the SNAP devices 204 of the AVS network 202 may provide network accessto, e.g., communications equipment 302, navigational sensors 304, ARINC429 data buses 306 and compatible legacy equipment 308, and AVS displays310. Similarly, the SNAP devices 204 of the MS network 208 may providenetwork access to, e.g., MIL-STD-1553 data buses 312 and compatiblelegacy equipment 314; sensor suites 316; MS displays 318; and missioncomputers 320. In some embodiments, the MS network 208 may be configuredin a mesh topology rather than the ring topology shown by, e.g., FIG. 2,whereby some SNAP devices 204 are directly connected (322) in additionto their ring neighbors on the MS network trunk 210. In embodiments, theSNAP devices 204 may provide district-level management for, e.g., powerdistribution and control; thermal management and adaptive cooling (e.g.,management of heat generated by the network components within adistrict); network access; I/O conversion and distribution; andencryption/decryption. For example, a SNAP device 204 may incorporateadditional software and/or hardware components depending on the DSAPservices provided within its district, as described in greater detailbelow.

Referring to FIG. 4, the aircraft 100, AVS network 202, and MS network208 is disclosed.

In embodiments, the MS network 208 (as well as the AVS network 202, notshown here in equivalent detail) may comprise multiple local areanetworks, connected via MS network trunks 210 a-b, for its essentialdistricts 102 and non-essential districts 104. For example, theessential district 102 a may include both essential and non-essentialnetwork components, serviced by essential SNAP devices 204 b andnon-essential SNAP device 204 c. Similarly, the essential district 102 bmay include essential SNAP device 204 b (with network bridging (212) toAVS SNAP device 204 d) and non-essential SNAP device 204 c. Thenon-essential districts 104 b-c may each include non-essential SNAPdevices 204 c (the latter SNAP device of the non-essential district 104c also incorporating network bridging 212 to AVS SNAP device 204 e), andthe non-essential district 104 d may include non-essential SNAP device204 c, which may serve as a subnetwork hub for the subnetwork 402.

In embodiments, each MS network trunk 210 a-b connecting a local areanetwork within the MS network 208 may incorporate backbone rings 404,406, 408. For example, a data ring 404 may provide primary control anddata functionality for the MS network 208. A dedicated video/sensor ring406 may provide high-bandwidth raw video (e.g., main cameras/heads-updisplays, weather radar, fire control, forward-looking infrared radar(FLIR)). A time ring 408 may provide accurate and time-sensitivedistribution of precise timing synchronization information throughoutthe MS network 208 and, through the SNAP devices 204 b-e, to networkcomponents and devices served by the SNAP devices.

Referring now to FIG. 5, the SNAP device 204 is disclosed.

In embodiments, the SNAP device 204 may include network trunk ports 502capable of accepting network trunk connections (e.g., AVS network trunk(FIG. 2, 206), MS network trunk (FIG. 2, 210) for incorporation into anAVS network (FIG. 2, 202) or MS network (FIG. 2, 208). The SNAP device204 may include additional device ports 504 for accepting physical links(e.g., coaxial, fiber, copper) to AVS or MS network components ordevices within a district served by the SNAP device.

In embodiments, each SNAP device 204 may be capable of controllingmultiple standard functions, e.g., cybersecurity, trunk networking,power control and distribution, district networking, and adaptivecooling/thermal management. In some embodiments, a SNAP device 204 maybe required to manage additional functionalities, e.g., powertransformation, district-level data concentration, and/or district-levelisolated power distribution

Referring also to FIG. 6, an adaptive I/O access point device 600 (AIAP,AdAPt) is disclosed. In embodiments, the SNAP device 204 may incorporatean AIAP device 600 in order to provide network access to, and dataexchange with, a fiber optic MS network (FIG. 2, 208) or AVS network(FIG. 2, 202) and legacy network components or equipment via deviceports 602, e.g., legacy equipment (FIG. 3: 308, 314) compatible withMIL-STD-1553 and/or ARINC 429 data buses (FIG. 3: 306, 312) or, e.g.,discrete or serial interfaces. In some embodiments, the AIAP device 600may incorporate additional components, e.g., for data guard and/orencryption/decryption capabilities, as described in greater detailbelow.

Referring to FIG. 7A and 7B, the SNAP device 204 is disclosed.

Referring in particular to FIG. 7A, the SNAP device 204 may include, inaddition to network trunk ports 502 and device ports 504 (e.g., districtswitch ports), network bridging ports 702 for accepting network bridging(FIG. 2, 212), e.g., to an AVS network (FIG. 2, 202) if the SNAP device204 is part of an MS network (FIG. 2, 208), or to the MS network if theSNAP device is part of the AVS network.

In embodiments, the SNAP device 204 may include a ring switch 704 andnetwork processors 706 for handling data exchanges and componentmanagement within the district served by the SNAP device. Referring alsoto FIG. 7B, the network processors 706 may include time managementmodules 708 (e.g., capable of sending or receiving timing informationvia the time ring (FIG. 4, 408)), device/network management modules 710,cybersecurity management modules 712, power management modules 714, andnetwork endpoints 716. The bridge core 718 may connect the networkprocessors 706 to the network trunk ports 502 and device ports 504. Itis contemplated that the SNAP device 204 may support a 10 Gb MS network208 with a growth path to 100 Gb.

Referring also to FIG. 7C, the SNAP device 204 f may be implemented andmay function similarly to the SNAP devices 204, 204 a-e of FIGS. 1through 7B, except that the SNAP device 204 f may incorporate an AIAPdevice 600 via a device port 504.

In embodiments, the SNAP device 204 f may (e.g., via power managementmodules (FIG. 7B, 714)) control the distribution of operating power tonetwork components and devices within its district. For example, theSNAP device 204 f may incorporate power converters 720 capable ofreceiving operating power from an aircraft power supply 722 and, viaelectronic circuit breakers 724 (ECB), supplying operating power to theAIAP device 600 and/or legacy network components and devices (726)served by the SNAP device 204 f via the AIAP device. For example, thepower converters 720 may convert received 270V operating power to 28Vfor distribution to the network components and devices. In someembodiments, the SNAP device 204 f may control the distribution ofoperating power through a local battery 728.

In embodiments, additional functionalities provided by the AIAP device600 (e.g., to legacy network components and devices via AIAP deviceports 602) may be managed by local processors 730. Referring also toFIG. 7D, in embodiments, the AIAP local processors 730 may incorporateAIAP device and I/O management modules 732, cybersecurity managementmodules 734, and an edge I/O core 736 for control of, e.g., generalcomputing 736 a, data guarding 736 b, data relay and routing 736 c, datatransformation 736 d (e.g., between copper/wired and fiber-opticcomponents), data encryption/decryption 736 e, and network endpointservices 736 f.

Referring to FIG. 8A, the AIAP device 600 a may be implemented and mayfunction similarly to the AIAP device 600 of FIGS. 6 through 7D, exceptthat the AIAP device 600 a appended to the SNAP device 204 (e.g., viadevice port 504) may incorporate a district-level data concentrator unit802 (DCU) and/or district-level Ethernet switch 804 (e.g., to providenetwork access for Ethernet network components to a fiber-optic MSnetwork (FIG. 2, 208).

In some embodiments, the SNAP device 204 and AIAP device 600 a mayconnect to existing cross-domain guard and/or Multiple Levels ofSecurity (MLS) encryption/decryption equipment to provide addedcybersecurity for district-level legacy network components and deviceshaving security classifications different than the MS network 208.Referring to FIG. 8B, the AIAP device 600 b may be implemented and mayfunction similarly to the AIAP devices 600, 600 a of FIGS. 6 through 8A,except that the AIAP device 600 b may incorporate cross-domain guardfunctionality 806 and MLS encryption/decryption 808 (e.g., via AIAPcybersecurity management modules (FIG. 7D, 732)) for providingcybersecurity and data guard services incorporating multiple levels ofassurance to legacy network components and devices (726).

Referring to FIG. 9, the AIAP device 600 is disclosed.

In embodiments, the AIAP device 600 may provide signal conditioning, MLSdata guarding, and/or encryption and decryption of data exchangedbetween legacy components and devices (e.g., connected via AIAP deviceports 602) and the MS network (FIG. 2, 208), e.g., USB-connectedcomponents (902); Ethernet links and/or networking components (904);Avionics Full-Duplex Switched Ethernet (AFDX) and other like ARINC664-compatible components (906); MIL-STD-1553 data buses (308); ARINC429 data buses (306); serial connections and/or components (908; e.g.,RS-232, RS-422, RS-485); analog network components (910); anddiscrete-port connected components (912).

For example, as described above if the AIAP device incorporates MLSencryption/decryption (FIG. 8B, 808) and/or cross-domain guarding (FIG.8B, 806) as described above. Further, the AIAP device 600 may providedata relay and routing, multiplexing (muxing) and demultiplexing(demuxing) and transformation of exchanged data between networkcomponents (e.g., copper-to-fiber, fiber-to-copper, fiber-to-fiber,copper-to-copper).

Referring to FIG. 10, an AIAP backplane implementation 1000 isdisclosed. The AIAP backplane implementation 1000 may include multipleAIAP devices 600.

In embodiments, the AIAP backplane implementation 1000 may provideaccess to the MS network (FIG. 2, 208) via the AIAP devices 600 tofiber-optic and legacy network components and devices, e.g., viafiber-optic connections 1002 or legacy wired connections (including, butnot limited to, Ethernet links and/or cables 904; serial connections908; ARINC 429 data buses 306; and MIL-STD-1553 data buses 308).Connected network component and devices may include, but are not limitedto, mission computers 320; sensor suites (FIG. 3, 316; e.g., flightsensor suites 1004, mission sensors 1006, cameras/image sensors 1008);input devices 1010; AFDX and other Ethernet switches 906; flightcomputers 1012; display systems (e.g., flight crew displays 1014,mission displays 1016).

CONCLUSION

It is to be understood that embodiments of the methods disclosed hereinmay include one or more of the steps described herein. Further, suchsteps may be carried out in any desired order and two or more of thesteps may be carried out simultaneously with one another. Two or more ofthe steps disclosed herein may be combined in a single step, and in someembodiments, one or more of the steps may be carried out as two or moresub-steps. Further, other steps or sub-steps may be carried in additionto, or as substitutes to one or more of the steps disclosed herein.

Although inventive concepts have been described with reference to theembodiments illustrated in the attached drawing figures, equivalents maybe employed and substitutions made herein without departing from thescope of the claims. Components illustrated and described herein aremerely examples of a system/device and components that may be used toimplement embodiments of the inventive concepts and may be replaced withother devices and components without departing from the scope of theclaims. Furthermore, any dimensions, degrees, and/or numerical rangesprovided herein are to be understood as non-limiting examples unlessotherwise specified in the claims.

We claim:
 1. An aircraft mission systems (MS) network architecture,comprising: a plurality of districts, each district associated with aphysical subdivision of an aircraft, each district comprising: at leastone first MS smart network access point (SNAP) device configured toconnect a MS network to one or more MS components disposed within thedistrict, the MS network comprising a plurality of MS SNAP devicescommunicatively connected in a first topology via a network trunk; atleast one first air vehicle systems (AVS) SNAP device configured toconnect an AVS network to one or more AVS components disposed within thedistrict, the AVS network comprising a plurality of AVS SNAP devicescommunicatively connected in a second topology via a second networktrunk; and the MS network including at least one second MS SNAP devicecommunicatively coupled to a second AVS SNAP device of the AVS networkvia a guarded network bridge.
 2. The aircraft MS network architecture ofclaim 1, wherein the district is an essential district including atleast one of: a mission-critical MS component operatively coupled to theMS SNAP device; and a mission-critical AVS component operatively coupledto the AVS SNAP device.
 3. The aircraft MS network architecture of claim1, wherein: the first topology is selected from a ring topology and amesh topology; and the second topology is a star topology.
 4. Theaircraft MS network architecture of claim 1, wherein the first networktrunk includes at least one fiber optic trunk.
 5. The aircraft MSnetwork architecture of claim 4, wherein the MS SNAP device includes atleast one adaptive input/output (I/O) component operatively coupled toone or more legacy MS components disposed within the district by a wiredinterface, the adaptive I/O component configured for data exchangebetween the MS network and the one or more legacy MS components.
 6. Theaircraft MS network architecture of claim 5, wherein the wired interfaceis selected from: a serial data bus according to MIL-STD-1553; anavionics data bus according to ARINC 429; and an Ethernet networkingcomponent.
 7. The aircraft MS network architecture of claim 5, whereinthe adaptive input/output (I/O) component includes at least one dataconcentrator unit (DCU).
 8. The aircraft MS network architecture ofclaim 5, wherein the adaptive input/output (I/O) component includes oneor more of a cross-domain guard and a multiple levels of security (MLS)encryption/decryption module.
 9. The aircraft MS network architecture ofclaim 1, wherein the first MS smart network access point (SNAP) deviceincludes one or more power control components configured to distributeoperating power to the one or more MS components.
 10. The aircraft MSnetwork architecture of claim 9, wherein the one or more power controlcomponents are selected from: a power converter operatively coupled to apower supply of the aircraft; an electronic circuit breaker (ECB); and alocal battery.